The fix for this is unfortunately complex. What should be done to resolve this in the general case is to not use simple integers for the binding names, but to use something like {identifier, num}. actually typing that out it might not be too hard, but it will take enough time that I don't think I can do it in the near future.

Please open an issue to track this work. If you or someone else would like to do it, the general pattern would be to:

1. generate a unique id for each query we generate. We can use something like System.monotonic_integer, or even make_ref. That parts not important really.
2. when we bind something, we add the query's id to the binding, i.e {id, binding}
3. Whenever we do a lateral join, we ensure that the query we are lateral joining to has its own identifier

Please remind me when you open the issue to add it to the roadmap under the "soon" category.

In the meantime, you can potentially accomplish what you need to accomplish with manual relationships or custom calculations.

Ok, opened the issue.

Yeah, I was using fragment workaround but thought about converting it into argumented calculation.

(Reminder about adding "soon" category to the issue.)